Document! X 2019
Building from Command Line, MSBUILD or Tfs / Building from Team Foundation Server
In This Topic
    Building from Team Foundation Server
    In This Topic

    Document! X 2019 includes a custom Workflow Activity which can be integrated with your Team Foundation Server 2010, 2012, 2013 or 2015 build process. If you are using Team Foundation Server 2008, refer to the Building with MSBUILD topic instead.

    Workflow Activity Assembly Location

    The Document! X 2019 Workflow Activity assembly file is named Innovasys.DocumentX.Build.dll and can be found in a \bin sub-directory below the Document! X installation path. The default bin path is c:\Program Files\Innovasys\DocumentX2019\bin\ .

    The Workflow Activity Assembly requires other Document! X assemblies and should not be moved from the installation path.

    Builds executed using the Workflow Activity require a full installation of Document! X. If you are integrating with a build on a build server, you must install a licensed copy of Document! X on the build server.

    Integrating with the Team Foundation Server Build Process

    The general process by which you customize the Team Foundation Server 2010 build process in order to include a custom activity is a complex subject and is not covered in detail here. The Team Foundation Build Customization Guide is a good place to start in understanding the Team Foundation Server build customization process.

    You can integrate the Document! X Workflow Activity as follows:

    1. Add the location of the Innovasys.DocumentX.Build.dll assembly (identified above) to your build process custom assembly path so that it can be found during the build process;
    2. Modify your custom Build process XAML file to add an instance of the ProjectBuildActivity. You would usually add such a custom activity at the end of the compilation activity;
    3. Set the ProjectFileName property of the Activity to the full path and filename of the Document! X project file you wish to build;
    4. Optionally set the BuildConfigurationName to the name of a specific BuildConfiguration defined in that project. If a BuildConfigurationName isn't specified, the first Build Profile will be built.
    See Also